-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update spack-stack-dev from spack develop as of 2024/10/31 #482
Update spack-stack-dev from spack develop as of 2024/10/31 #482
Conversation
Co-authored-by: Gava, Francesco <[email protected]> Co-authored-by: Bernhard Kaindl <[email protected]>
* e4s external rocm ci: upgrade to v6.2.1 * use ghcr.io/spack/spack/ubuntu22.04-runner-amd64-gcc-11.4-rocm6.2.1:2024.10.08 * magma +rocm: add entry for v6.2.1
Co-authored-by: LMS Bioinformatics <[email protected]>
* Updates Caliper recipe to build the new Python bindings * Implements setup_run_environment for Caliper to update PYTHONPATH
…k#47029) and add another backward compat bound for just 8.8
* e4s ci stacks: add fftx cpu, cuda, and rocm builds * disable fftx+rocm due to spack github issue spack#47034 * e4s oneapi: fftx has spack build error spack#47048
Co-authored-by: Bernhard Kaindl <[email protected]>
* voropp: migrate to cmake * lammps: update voropp dep
* Remove the implicit CORE-AVX512 since the CPU specific flags are added by the compiler wrappers. * Add `-i_use-path` to help `ifx` find `lld` even if `-gcc-name` is set in `ifx.cfg`. This file is written by `intel-oneapi-compilers` package to find the correct `gcc`. Not being able to find `ldd` is a bug in `ifx`. @rschon2 found this workaround.
…#47065) Turns out `os=...` of the spec and `MACOSX_DEPLOYMENT_TARGET` are kept in sync, and the env variable is used to initialize `CMAKE_MACOSX_DEPLOYMENT_TARGET`. In bootstrap code we set the env variable, so these bits are redundant. --------- Co-authored-by: haampie <[email protected]>
Some unused methods in VTK-m resulted in compile errors. These were not discovered because many compilers ignore unused methods in templated classes, but the SYCL compiler for Aurora gave an error.
Co-authored-by: Peter Scheibel <[email protected]>
Co-authored-by: Alex C Leute <[email protected]>
* py-coca-pytorch: new package * [py-coca-pytorch] black --------- Co-authored-by: Alex C Leute <[email protected]>
Co-authored-by: Alex C Leute <[email protected]>
Co-authored-by: Alex C Leute <[email protected]>
…ge.py, var/spack/repos/builtin/packages/libxkbcommon/package.py, var/spack/repos/builtin/packages/openmpi/package.py
…and lib/spack/spack/compilers/oneapi.py: set correct version ranges
I'll need a bit of time to look over this. It looks good so far, though I think it'll need one or two tweaks related to static libraries... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on my Mac (Sonoma 14.6.1, Command Line Tools 15.3, GNU Fortran 12.4.0), and it looks good. I was able to build jedi-bundle and I got the usual ctest failures (19) that we have been seeing on the mac.
@AlexanderRichert-NOAA Please make sure to push any changes here upstream afterwards. We want the packages to be 100% identical, if possible. I will create a PR for a3dd052 (cprnc) shortly. |
spack PR for the cprnc bug fix: spack#47505 |
@climbfuji yep will do, I'm keeping a log, and I'll also provide a summary here when I'm done going through the list of conflicts. |
Perfect, thanks a lot
…________________________________
From: Alex Richert ***@***.***>
Sent: Friday, November 8, 2024 3:00 PM
To: JCSDA/spack ***@***.***>
Cc: Dom Heinzeller ***@***.***>; Mention ***@***.***>
Subject: Re: [JCSDA/spack] Update spack-stack-dev from spack develop as of 2024/10/31 (PR #482)
@climbfuji<https://github.com/climbfuji> yep will do, I'm keeping a log, and I'll also provide a summary here when I'm done going through the list of conflicts.
—
Reply to this email directly, view it on GitHub<#482 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB5C2RKBODF3DS7REYMR33TZ7UYBRAVCNFSM6AAAAABQ7LW4EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVHAYTMNRWG4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Here's my summary of the packages that were manually fixed for conflicts: |
@@ -1,4 +1,4 @@ | |||
# Copyright 2013-2024 Lawrence Livermore National Security, LLC and other | |||
# Copyright 2013-2024 Lawrence Livermore National Security, LLC and other |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be reverted, or?
The upstream PR for the cprnc bug fix was merged |
Description
Update spack-stack-dev from spack develop as of 2024/10/31. The following files had merge conflicts that I needed to resolve and that I would like the reviewers to look at (there were a few more, but those I knew enough about to resolve with confidence):
Update 2024/11/08 Added commit a3dd052 to fix a bug in
cprnc
- the install rpaths for the netCDF libraries were missing, which caused the installations from the binary cache to fail during the relocation step:Testing
https://github.com/spack/spack